Technologies for flexible and automatic mapping of disaggregated network communication resources

ABSTRACT

Technologies for dynamic allocation of network communication resources includes a resource manager server to allocate a set of network communication resources to a compute device through an expansion bus switch that is coupled to the compute device and to the network communication resources. The resource manager server obtains telemetry data indicative of a present utilization of the allocated set of network communication resources and determines whether the present utilization satisfies a predefined utilization threshold. Additionally, the resource manager server adjusts, through the expansion bus switch and in response to a determination that the present utilization does not satisfy the predefined utilization threshold, an amount of network communication resources in the set to the compute device.

BACKGROUND

Current implementations of network communication resources, such asnetwork interface controllers (NICs), in data centers are staticallymapped to compute devices. That is, an orchestrator allocates a certainamount of NICs to a compute device to perform a workload (e.g.,applications, processes, etc.) based on the workload requirements.

The implementation of the NICs among the compute devices described aboveleads to difficulty in balancing the workload in the processors based onthe amount of network capacity because of issues with network density,bandwidth capacity of the NICs, and heterogeneity of the available NICs.As such, some of the NICS allocated to perform the workload may becomesaturated or underutilized since these NICS are allocated to aparticular compute device for performing a workload that may vary inbandwidth.

BRIEF DESCRIPTION OF THE DRAWINGS

The concepts described herein are illustrated by way of example and notby way of limitation in the accompanying figures. For simplicity andclarity of illustration, elements illustrated in the figures are notnecessarily drawn to scale. Where considered appropriate, referencelabels have been repeated among the figures to indicate corresponding oranalogous elements.

FIG. 1 is a simplified block diagram of at least one embodiment of asystem for dynamic allocation of network communication resources;

FIG. 2 is a simplified block diagram of at least one embodiment of aresource manager server of the system of FIG. 1 ;

FIG. 3 is a simplified block diagram of at least one embodiment of acompute device of the system of FIG. 1 ;

FIG. 4 is a simplified block diagram of at least one embodiment of anenvironment that may be established by the resource manager server ofFIGS. 1 and 2 ;

FIG. 5 is a simplified flow diagram of at least one embodiment of amethod for establishing predefined utilization thresholds for dynamicallocation of network communication resources that may be performed bythe resource manager server of FIGS. 1 and 2 ; and

FIGS. 6-7 are a simplified flow diagram of at least one embodiment of amethod for dynamic allocation of network communication resources thatmay be performed by the resource manager server of FIGS. 1 and 2 .

DETAILED DESCRIPTION OF THE DRAWINGS

While the concepts of the present disclosure are susceptible to variousmodifications and alternative forms, specific embodiments thereof havebeen shown by way of example in the drawings and will be describedherein in detail. It should be understood, however, that there is nointent to limit the concepts of the present disclosure to the particularforms disclosed, but on the contrary, the intention is to cover allmodifications, equivalents, and alternatives consistent with the presentdisclosure and the appended claims.

References in the specification to “one embodiment,” “an embodiment,”“an illustrative embodiment,” etc., indicate that the embodimentdescribed may include a particular feature, structure, orcharacteristic, but every embodiment may or may not necessarily includethat particular feature, structure, or characteristic. Moreover, suchphrases are not necessarily referring to the same embodiment. Further,when a particular feature, structure, or characteristic is described inconnection with an embodiment, it is submitted that it is within theknowledge of one skilled in the art to effect such feature, structure,or characteristic in connection with other embodiments whether or notexplicitly described. Additionally, it should be appreciated that itemsincluded in a list in the form of “at least one A, B, and C” can mean(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).Similarly, items listed in the form of “at least one of A, B, or C” canmean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).

The disclosed embodiments may be implemented, in some cases, inhardware, firmware, software, or any combination thereof. The disclosedembodiments may also be implemented as instructions carried by or storedon a transitory or non-transitory machine-readable (e.g.,computer-readable) storage medium, which may be read and executed by oneor more processors. A machine-readable storage medium may be embodied asany storage device, mechanism, or other physical structure for storingor transmitting information in a form readable by a machine (e.g., avolatile or non-volatile memory, a media disc, or other media device).

In the drawings, some structural or method features may be shown inspecific arrangements and/or orderings. However, it should beappreciated that such specific arrangements and/or orderings may not berequired. Rather, in some embodiments, such features may be arranged ina different manner and/or order than shown in the illustrative figures.Additionally, the inclusion of a structural or method feature in aparticular figure is not meant to imply that such feature is required inall embodiments and, in some embodiments, may not be included or may becombined with other features.

Referring now to FIG. 1 , a system 100 for automatic mapping ofdisaggregated network communication resources is shown. In theillustrative embodiment, automatic mapping of disaggregated networkcommunication resources may include a data center resource manager 102allocating network communication resources to compute devices through anexpansion bus switch 118 in the system 100. The data center resourcemanager 102 may be embodied as a resource manager server, described inmore detail herein. In the illustrative embodiment, the data centerresource manager 102 obtains telemetry data indicative of a presentutilization of the allocated set of network communication resources anddetermine whether the present utilization satisfies a predefinedutilization threshold. Accordingly, the data center resource manager 102adjusts the amount of network communication resources in the set to thecompute device in response to a determination that the presentutilization does not satisfy the predefined utilization threshold. Forexample, the data center resource manager 102 may obtain a service levelagreement that includes service level agreement data indicative of thepredefined utilization threshold to be satisfied in association with aworkload executed by the compute device. That is, there are performancerequirements executed by the compute device in processing a workload.

In the illustrative embodiment, the system 100 includes the data centerresource manager 102 in communication with pods 104 a-c through anetwork 106. Each pod 104 a-c includes a pod resource manager 110, oneor more compute devices 112, an expansion bus switch 118, and one ormore network interface controllers (NICs) 120, which may also bereferred to as host fabric interfaces (HFIs) when applied to high speedfabrics, and may be referred to herein as network communicationresources. Although only three pods, two compute devices, and four NICsare shown, there may be any number of pods, compute devices, and/or NICsutilized in the system 100. The system 100 may be embodied as a datacenter and provide storage and compute services (e.g., cloud services)to a client device (not shown) that is in communication with the system100 through a network 106. In the illustrative embodiment, each computedevice 112 utilizes a central processing unit (CPU) 114 to execute aworkload 116 (e.g., an application). Additionally, each pod 104 a-cincludes an expansion bus switch 118, which may be embodied as anydevice or circuitry (e.g., a Peripheral Component Interconnect Express(PCIe) switch, or a switch based on another data sharing mechanism suchas a coherent memory link) capable of allocating network communicationresources to the compute devices 112. In other embodiments, one or moreof the pods 104 a-c, may include other devices or circuitry capable ofaccelerating the execution of a workload, such as anapplication-specific integrated circuit, a co-processor, etc. In theillustrative embodiment, the one or more NICs 120 may include atelemetry logic unit 122. The telemetry logic unit 122 may be configuredto determine the present utilization of the NICs 120 and determinewhether the present utilization satisfies a predefined utilizationthreshold. The telemetry logic unit 122 may identify when the presentutilization exceeds the predefined utilization threshold for apredetermined amount of time (e.g., at least one minute).

In the illustrative embodiment, the network communication resources,embodied as NICs 120, are shared between the compute devices 112. Thepod resource manager 110 or the data center resource manager 102 mayallocate the NICs 120 to a compute device 112 through the expansion busswitch 118 based on the amount of network communication resourcesrequired by the compute device and a service level agreement thatdefines the target performance of the workload executed by the computedevice 112. That is, one or more NICs 120 and/or a portion of one ormore NICs 120 may be allocated to the compute devices 112. In operation,the system 100 may utilize one or more NICs 120 to produce telemetrydata through the telemetry logic unit 122 indicative of the presentutilization of the NICs 120 for use by the data center resource manager102 or the pod resource manager 110. In some embodiments, the NICs 120may produce data indicative of a determination of whether the presentutilization satisfies the predefined utilization threshold as describedabove. In some embodiments, the compute devices 112 may produce thetelemetry data for the data center resource manager 102 or the podresource manager 110. The telemetry data provides information on thepresent utilization of the allocated set of network communicationresources. For example, whether a NIC 120 is saturated or underutilized.From this, the pod resource manager 110 or data center resource manager102 adjusts the amount of network communication resources to the computedevice 112 through the expansion bus switch 118. Thereby, the system 100reduces saturation of the network communication resources (e.g., NICs120) or underutilization of the network communication resources. Inorder to adjust the network communication resources accordingly, the podresource manager 110 or the data center resource manager 102 determineswhether the present utilization satisfies a predefined utilizationdefined by the service level agreement as described above. For example,the pod resource manager 110 compares whether the present utilization iswithin 40-80% of data communication capacity of the NICs 120 presentlyallocated to the compute devices 112. In some embodiments, thecomparison may be used to determine if the predefined utilizationthresholds have been exceeded for a predetermined amount of time asdescribed above. The pod resource manager 110 may adjust the allocationof the NICs 120 to ensure the present utilization meets the predefinedthresholds.

Referring now to FIG. 2 , the data center resource manager 102 or thepod resource manager 110 may be embodied as a resource manager server202 capable of performing the functions described herein, includingallocation of the NICs 120 to the compute devices 112 to perform aworkload 116. As shown in FIG. 2 , the illustrative resource managerserver 202 includes a compute engine 204, a communication circuitry 206,one or more data storage devices 208, and an expansion bus switchinterface 210. In some embodiments, the resource manager server 202 mayinclude peripheral devices 212. Of course, in other embodiments, theresource manager server 202 may include other or additional components,such as those commonly found in a server. Additionally, in someembodiments, one or more of the illustrative components may beincorporated in, or otherwise form a portion of, another component.

The compute engine 204 may be embodied as any type of device orcollection of devices capable of performing various compute functionsdescribed below. In some embodiments, the compute engine 204 may beembodied as a single device such as an integrated circuit, an embeddedsystem, a field-programmable gate array (FPGA), a system-on-a-chip(SOC), or other integrated system or device. Additionally, in someembodiments, the compute engine 204 includes or is embodied as a centralprocessing unit (CPU) 214 and a memory 216. The CPU 214 may be embodiedas any type of processor capable of performing the functions describedherein. For example, the CPU 214 may be embodied as a single ormulti-core processor(s), a microcontroller, or other processor orprocessing/controlling circuit. In some embodiments, the CPU 214 may beembodied as, include, or be coupled to an FPGA, an application specificintegrated circuit (ASIC), reconfigurable hardware or hardwarecircuitry, or other specialized hardware to facilitate performance ofthe functions described herein.

The memory 216 may be embodied as any type of volatile (e.g., dynamicrandom access memory (DRAM), etc.) or non-volatile memory or datastorage capable of performing the functions described herein. Volatilememory may be a storage medium that requires power to maintain the stateof data stored by the medium. Non-limiting examples of volatile memorymay include various types of random access memory (RAM), such as dynamicrandom access memory (DRAM) or static random access memory (SRAM). Oneparticular type of DRAM that may be used in a memory module issynchronous dynamic random access memory (SDRAM). In particularembodiments, DRAM of a memory component may comply with a standardpromulgated by JEDEC, such as JESD79F for DDR SDRAM, JESD79-2F for DDR2SDRAM, JESD79-3F for DDR3 SDRAM, JESD79-4A for DDR4 SDRAM, JESD209 forLow Power DDR (LPDDR), JESD209-2 for LPDDR2, JESD209-3 for LPDDR3, andJESD209-4 for LPDDR4 (these standards are available at www.jedec.org).Such standards (and similar standards) may be referred to as DDR-basedstandards and communication interfaces of the storage devices thatimplement such standards may be referred to as DDR-based interfaces.

In one embodiment, the memory device is a block addressable memorydevice, such as those based on NAND or NOR technologies. A memory devicemay also include future generation nonvolatile devices, such as a threedimensional crosspoint memory device, or other byte addressablewrite-in-place nonvolatile memory devices. In one embodiment, the memorydevice may be or may include memory devices that use chalcogenide glass,multi-threshold level NAND flash memory, NOR flash memory, single ormulti-level Phase Change Memory (PCM), a resistive memory, nanowirememory, ferroelectric transistor random access memory (FeTRAM),anti-ferroelectric memory, magnetoresistive random access memory (MRAM)memory that incorporates memristor technology, resistive memoryincluding the metal oxide base, the oxygen vacancy base and theconductive bridge Random Access Memory (CB-RAM), or spin transfer torque(STT)-MRAM, a spintronic magnetic junction memory based device, amagnetic tunneling junction (MTJ) based device, a DW (Domain Wall) andSOT (Spin Orbit Transfer) based device, a thyristor based memory device,or a combination of any of the above, or other memory. The memory devicemay refer to the die itself and/or to a packaged memory product.

In some embodiments, 3D crosspoint memory may comprise a transistor-lessstackable cross point architecture in which memory cells sit at theintersection of word lines and bit lines and are individuallyaddressable and in which bit storage is based on a change in bulkresistance. In operation, the memory 216 may store various software anddata used during operation such as telemetry data, threshold utilizationdata, resource allocation data, applications, programs, libraries, anddrivers.

The communication circuitry 206 may be embodied as any communicationcircuit, device, or collection thereof, capable of enablingcommunications over a network 106 between the pods 104 a-c and the datacenter resource manager 102. The communication circuitry 206 may beconfigured to use any one or more communication technology (e.g., wiredor wireless communications) and associated protocols (e.g., Ethernet,Bluetooth®, Wi-Fi®, WiMAX, etc.) to effect such communication. The NIC218 may similarly be embodied as any communication circuit, device, orcollection thereof, capable of enabling communications over a network106 between the pods 104 a-c and the data center resource manager 102.

The data storage device(s) 208 may be embodied as any type of device ordevices configured for short-term or long-term storage of data such as,for example, memory devices and circuits, memory cards, hard diskdrives, solid-state drives, non-volatile flash memory, or other datastorage devices. The expansion bus switch interface 210 may be embodiedas any type of device and/or circuitry configured for communicating withan expansion bus switch (e.g., a Peripheral Component InterconnectExpress (PCIe) switch) to connect to the network communication resourcesof the system 100.

As mentioned above, in some embodiments, the resource manager server 202may include one or more peripheral devices 212. Such peripheral devices212 may include any type of peripheral device commonly found in a serverand/or compute device such as a display, speakers, a mouse, a keyboard,and/or other input/output devices, interface devices, and/or otherperipheral devices.

The pod resource manager 110 may have components similar to thosedescribed in FIG. 2 . The description of those components of theresource manager server 202 is equally applicable to the description ofcomponents of the pod resource manager 110 and is not repeated hereinfor clarity of the description. Further, it should be appreciated thatthe pod resource manager 110 may include other components,sub-components, and devices commonly found in a computing device and/orserver, which are not discussed above in reference to the resourcemanager server 202 and not discussed herein for clarity of thedescription.

Referring now to FIG. 3 , the compute device 112, which may have similarcomponents to the resource manager server 202, may be embodied as anytype of compute device capable of performing the functions describedherein, including executing a workload 116. As shown in FIG. 3 , theillustrative compute device 112 includes a compute engine 304, anexpansion bus switch interface 306, one or more data storage devices308, and one or more NICs 310. In some embodiments, the compute device112 may include peripheral devices 312. Of course, in other embodiments,the compute device 112 may include other or additional components, suchas those commonly found in a compute device. Additionally, in someembodiments, one or more of the illustrative components may beincorporated in, or otherwise form a portion of, another component.

The compute engine 304 may be embodied as any type of device orcollection of devices capable of performing various compute functionsdescribed below. In some embodiments, the compute engine 304 may beembodied as a single device such as an integrated circuit, an embeddedsystem, a field-programmable gate array (FPGA), a system-on-a-chip(SOC), or other integrated system or device. Additionally, in someembodiments, the compute engine 304 includes or is embodied as a centralprocessing unit (CPU) 314 and a memory 316. The CPU 314 may be embodiedas any type of processor capable of performing the functions describedherein. For example, the CPU 314 may be embodied as a single ormulti-core processor(s), a microcontroller, or other processor orprocessing/controlling circuit. In some embodiments, the CPU 314 may beembodied as, include, or be coupled to an FPGA, an application specificintegrated circuit (ASIC), reconfigurable hardware or hardwarecircuitry, or other specialized hardware to facilitate performance ofthe functions described herein.

The memory 316 may be embodied as any type of volatile (e.g., dynamicrandom access memory (DRAM), etc.) or non-volatile memory or datastorage capable of performing the functions described herein, similarlyto memory 216.

The expansion bus switch interface 306 may be embodied as any type ofdevice and/or circuitry configured for communicating with an expansionbus switch (e.g., a Peripheral Component Interconnect Express (PCIe)switch) to connect to the network communication resources of the system100.

The data storage device(s) 308 may be embodied as any type of device ordevices configured for short-term or long-term storage of data such as,for example, memory devices and circuits, memory cards, hard diskdrives, solid-state drives, non-volatile flash memory, or other datastorage devices.

The NIC(s) 310 may be embodied as any communication circuit, device, orcollection thereof, capable of enabling communications over a network106 between the data center resource manager 102 and the pods 104 a-c.The NIC(s) 310 may be configured to use any one or more communicationtechnology (e.g., wired or wireless communications) and associatedprotocols (e.g., Ethernet, Bluetooth®, Wi-Fi®, WiMAX, etc.) to effectsuch communication.

As mentioned above, in some embodiments, the compute device 112 mayinclude one or more peripheral devices 312. Such peripheral devices 312may include any type of peripheral device commonly found in a computedevice such as a display, speakers, a mouse, a keyboard, and/or otherinput/output devices, interface devices, and/or other peripheraldevices.

As described above, the data center resource manager 102 and pods 104a-c are illustratively in communication via a network 106, which may beembodied as any type of wired or wireless communication network,including global networks (e.g., the Internet), local area networks(LANs) or wide area networks (WANs), cellular networks (e.g., GlobalSystem for Mobile Communications (GSM), 3G, Long Term Evolution (LTE),Worldwide Interoperability for Microwave Access (WiMAX), etc.), digitalsubscriber line (DSL) networks, cable networks (e.g., coaxial networks,fiber networks, etc.), or any combination thereof.

Referring now to FIG. 4 , the resource manager server 202 may establishan environment 400 during operation. The data center resource manager102 and the pod resource manager 110 and their components may besimilarly embodied as the resource manager server 202 and establish theenvironment 400 during operation. The illustrative environment 400includes a network communicator 402 and an allocation manager 404. Eachof the components of the environment 400 may be embodied as hardware,firmware, software, or a combination thereof. As such, in someembodiments, one or more of the components of the environment 400 may beembodied as circuitry or a collection of electrical devices (e.g.,network communicator circuitry 402, allocation manager circuitry 404,etc.). It should be appreciated that, in such embodiments, one or moreof the network communicator circuitry 402 or allocation managercircuitry 404 may form a portion of one or more of the compute engine204, communication circuitry 206, one or more data storage device(s)208, expansion bus switch interface 210, and/or any other components ofthe resource manager server 202. In the illustrative embodiment, theenvironment 400 includes telemetry data 412, which may be embodied asany data established by the data center resource manager 102 and/or pods104 a-c during the execution of one or more workloads by the computedevices 112 and indicative of the present utilization of networkcommunication resources by the compute devices 112. For example, thepresent utilization may be indicated as a percentage of the maximumthroughput of the network communication resources (e.g. NICs 120), suchas 80% of a NIC's 120 capacity. The telemetry data 412 may include alertnotifications that utilization thresholds have been exceeded andnotifications that utilization thresholds are satisfied. Furthermore,telemetry data 412 may include physical telemetry data (e.g. powerutilization, thermal, etc.) and performance data provided by performancemonitor agents (PMON). For example, the telemetry logic unit 122 of theNICs 120 may be embodied as or contain the PMON. Additionally, theillustrative environment 400 includes threshold utilization data 414which may be embodied as any data indicative of the utilizationthresholds that define a percentage of the maximum throughput that isallowed for the NICs 120 before an adjustment is made to reduce orincrease the utilization of the NICs 120. The thresholds may be definedby a service level agreement as described above. In addition, theillustrative environment 400 includes resource allocation data 416 whichmay be embodied as any data indicative of the NICs 120 present on eachexpansion bus switch 118 and the capabilities of each NIC 120 (e.g. maxthroughput). For example, one NIC 120 may have a bandwidth of 10gigabytes (GB) and another NIC 120 may have a bandwidth of 40 GB. Fromthis information, the resource allocation data 416 compiles the amountof network communication resources available to be allocated to computedevices 112. Furthermore, the pods 104 a-c may communicate with oneanother to share the network communication resources available to oneanother.

In the illustrative environment 400, the network communicator 402, whichmay be embodied as hardware, firmware, software, virtualized hardware,emulated architecture, and/or a combination thereof as discussed above,is configured to facilitate inbound and outbound network communications(e.g., network traffic, network packets, network flows, etc.) to andfrom the resource manager server 202, respectively. To do so, thenetwork communicator 402 is configured to receive and process datapackets from one system or computing device (e.g., a pods 104 a-c and/ordata center resource manager 102) and to prepare and send data packetsto another computing device or system (e.g., a pods 104 a-c and/or datacenter resource manager 102). Accordingly, in some embodiments, at leasta portion of the functionality of the network communicator 402 may beperformed by the communication circuitry 206, and, in the illustrativeembodiment, by the NIC 218.

The allocation manager 404, which may be embodied as hardware, firmware,software, virtualized hardware, emulated architecture, and/or acombination thereof, is configured to allocate the network communicationresources (e.g. NICs 120) to a compute device 112 to perform a workload116. To do so, in the illustrative embodiment, the allocation manager404 includes a utilization threshold identifier 406, a telemetrycomparator 408, and a switch configurator 410. The utilization thresholdidentifier 406, in the illustrative environment, is configured toretrieve data from the threshold utilization data 414 in order todetermine the predefined threshold to appropriately limit saturation andunderutilization of the network communication resources. The utilizationthreshold identifier 406 may also set the predefined utilizationthresholds by determining the predefined utilization thresholds from aninput from an administrator or a service level agreement that indicatesthe desired performance for a compute device 112. For example, a clientmay require the compute device 112 to perform a workload with relativelylow latency and as such yield a lower utilization threshold that needsto be satisfied by not exceeding that threshold. The utilizationthresholds may define both a lower end and higher end that need to besatisfied by not exceeding those thresholds. That is, the utilization ofthe network communication resources must be within a certain range of apercentage of the max throughput.

The telemetry comparator 408, in the illustrative embodiment, isconfigured to retrieve the telemetry data 412 to determine the presentutilization of the network communication resources and compare thepresent utilization to the utilization thresholds identified by theutilization threshold identifier 406. The telemetry data 412 may also becollected from the NICs 120 and/or the expansion bus switch 118. To doso, the telemetry comparator 408 determines whether the presentutilization exceeds the utilization thresholds to determine whether anadjustment of the network communication resources is required or if thepresent utilization satisfies the utilization thresholds. For example,if the utilization thresholds were set to be between 20-80% and thepresent utilization is 90%, the telemetry comparator 408 would determinean adjustment is required to reduce the present utilization to withinthe utilization thresholds.

The switch configurator 410, in the illustrative embodiment, isconfigured to perform an adjustment of the network communicationresources allocated to a compute device 112 by communicating with theexpansion bus switch 118 and redirecting one or more NICs 120 or aportion of the one or more NICs 120 to or away from the compute device112 that is performing the workload 116. The switch configurator 410 maybe configured to greatly adjust the present utilization of the set ofallocated network communication resources by, for example, allocatingmore NICs 120 to the compute device 112. In other embodiments, theswitch configurator 410 may be configured to slightly reduce the presentutilization of the set of allocated network communication resources by,for example, allocating fewer NICs 120 to the compute device 112. Insome embodiments, the switch configurator 410 may reallocate the networkcommunication resources to generate a new utilization that is within theutilization thresholds. In addition, in some embodiments, the switchconfigurator 410 may force utilization of network communicationresources to go to zero for maintenance or power efficiency, etc. In theillustrative embodiment, when the switch configurator 410 performs aforced decrease in utilization, the telemetry comparator 408 excludesany network resource utilization data associated with such instances inthe determination of whether to adjust the network communicationresources.

Referring now to FIG. 5 , in use, a resource manager server 202 mayexecute a method 500 for establishing predefined thresholds for dynamicallocation of network communication resources (e.g. NICs 120) within asystem 100 that includes pods 104 a-c and data center resource manager102. For simplicity, the method 500 is described below as beingperformed by the resource manager server 202. However, it should beunderstood that in other embodiments, the method 500 may be performed byone or more other devices (e.g. pods 104 a-c and/or data center resourcemanager 102). The method 500 begins with block 502 in which the resourcemanager server 202 determines whether there is a need to establishpredefined utilization thresholds that a compute device 112 performing aworkload 116 is required to meet. In the illustrative embodiment, thepredefined utilization thresholds establish both a low end utilizationthreshold and a high end utilization threshold that the compute device112 may not exceed. This is to avoid underutilization of the networkcommunication resources and saturation of the network communicationresources as described above. The establishment of predefined thresholdsmay include establishing initial utilization thresholds or updatingpreviously-used utilization thresholds. If the resource manager server202 determines there is a need to establish predefined utilizationthresholds, the method 500 advances to block 504. However, if there isno need to establish predefined utilization thresholds, then the method500 loops back to the start of block 502.

In block 504, the resource manager server 202 obtains a service levelagreement that contains service level agreement data indicative of thepredefined threshold utilizations to be satisfied in association with aworkload 116 executed by a compute device 112. That is, the servicelevel agreement may define a performance requirement for the computedevice 112 performing the workload 116, such as whether a particularlatency limit is required for performing the workload 116.

In block 506, the resource manager server 202 determines the predefinedutilization thresholds from the service level agreement. For example, ifa certain amount of bandwidth is required with a low latency, then theresource manager server 202 may set the predefined utilizationthresholds to take into account the parameters of the service levelagreement.

After determination of the predefined utilization thresholds, the method500 advances to block 508 in which the resource manager server 202provides the threshold data indicative of the utilization thresholds tothe network communication resources. In some embodiments, the resourcemanager server 202 may provide the threshold data to the compute devices112 and/or NICs 120. As a result, the compute devices 112 and/or NICs120 may analyze the telemetry data indicative of a present utilizationand determine whether the present utilization satisfies the predefinedutilization thresholds (e.g. are within the thresholds). The NICs 120may utilize the telemetry logic units 122 in order to perform thedetermination.

Referring now to FIG. 6 , in use, a resource manager server 202 mayexecute a method 600 for dynamic allocation of network communicationresources (e.g. NICs 120) within a system 100 that includes pods 104 a-cand data center resource manager 102. For simplicity, the method 600 isdescribed below as being performed by the resource manager server 202.However, it should be understood that in other embodiments, the method600 may be performed by one or more other devices (e.g. pods 104 a-c).The method 600 begins with block 602 in which the resource managerserver 202 allocates a set of network communication resources, such asNICs 120, to a compute device 112. To do so, in some embodiments, theresource manager server 202 may, in block 604, use an expansion busswitch 118 coupled to the compute device 112 to allocate the set ofnetwork communication resources. Furthermore, in some embodiments, inblock 606, the resource manager server 202 may allocate a differentamount of network communication resources to another compute device 112connected to the expansion bus switch 118. As such, the resource managerserver 202 may allocate network communication resources to a pluralityof compute devices 112 connected to the expansion bus switch 118. Insome embodiments, the resource manager server 202 may also allocatenetwork communication resources to other computes devices within thesystem 100. In some embodiments, in block 608, the resource managerserver 202 may allocate a portion of a total network communicationcapacity of a NIC 120 to the compute device 112. For example, if a NIC's120 total capacity is 40 GB, then the resource manager server 202 mayallocate 20 GB of the NIC's 120 total capacity to the compute device112. In some embodiments, the resource manager server 202 may allocatethe set of network communication resources through a peripheralcomponent interconnect express (PCIE) bus switch, as indicated in block610. In other embodiments, the resource manager server 202 may allocatethe set of network communication resources through a coherent memorylink.

Subsequent to allocation of the set of network communication resourcesto the compute device 112, in block 612 the resource manager server 202determines whether to perform dynamic allocation of the networkcommunication resources. If it is determined that the resource managerserver 202 is to perform dynamic allocation of the network communicationresources, then the method 600 advances to block 614. However, if thereis no need to perform dynamic allocation of the network communicationresources (e.g., if a configuration setting indicates to enable dynamicallocation of network communication resources), then the method 600loops back to the beginning of block 612 to continue monitoring whetherdynamic allocation is needed.

In block 614, the resource manager server 202 obtains telemetry dataindicative of present utilization of the allocated set of networkcommunication resources. To do so, in some embodiments, in block 616,the resource manager server 202 obtains the telemetry data from thecompute device 112. In addition, in some embodiments, in block 618, theresource manager server 202 obtains the telemetry data from one or moreNICs 120.

Referring now to FIG. 7 , in block 620, the resource manager server 202determines whether the present utilization satisfies the predefinedutilization thresholds. In the illustrative embodiment, the resourcemanager server 202 may compare the present utilization determined fromthe telemetry data to the predefined utilization thresholds to determinewhether the present utilization is within the predefined utilizationthresholds. In some embodiments, in block 622, the resource managerserver 202 may obtain a notification from the set of networkcommunication resources indicative of whether a predefined utilizationthreshold is presently satisfied. That is, the network communicationresources may also perform the determination with the threshold datastored on the network communication resources.

In block 624, the resource manager server 202 determines whether thepredefined utilization thresholds were satisfied. If the resourcemanager server 202 determines that the predefined utilization thresholdswere satisfied, then the method 600 returns to block 614 of FIG. 6 tocontinue obtaining telemetry data to monitor the present utilizationagainst the predefined utilization thresholds. However, if the resourcemanager server 202 determines that one or more predefined utilizationthresholds were not met, then the method 600 advances to block 626 inwhich the resource manager server 202 adjusts the amount of networkcommunication resources to be allocated to the compute device 112. To doso, in some embodiments, in block 628, the resource manager server 202may produce a request to the expansion bus switch 118 to adjust theallocation of the network communication resources of the compute device112 associated with the workload for which each predefined networkutilization threshold was not satisfied. That is, the resource managerserver 202 may allocate more network communication resources or removesome network communication resources to the compute device 112. Inaddition, in some embodiments, in block 630, the resource manager server202 may produce a request to another resource manager server that iscommunicatively coupled to the expansion bus switch 118 to allocate morenetwork communication resources (e.g., if network communicationresources from another pod are also connected to the expansion busswitch 118). For example, a pod 104 a may communicate with pod 104 b torequest additional network communication resources to be allocated tothe compute device 112. In some embodiments, the resource manager server202 may adjust a link speed associated with one or more of the networkcommunication resources, adjust a number of links between two devices inthe network (e.g., between the compute device 112 and another computedevice), and/or adjust traffic shaping parameters. After performing theadjustment, the method 600 returns to block 614 of FIG. 6 to continueobtaining telemetry data to monitor the present utilization against thepredefined utilization thresholds.

EXAMPLES

Illustrative examples of the technologies disclosed herein are providedbelow. An embodiment of the technologies may include any one or more,and any combination of, the examples described below.

Example 1 includes a resource manager server comprising a compute engineto allocate a set of network communication resources to a compute devicethrough an expansion bus switch coupled to the compute device and to thenetwork communication resources; obtain telemetry data indicative of apresent utilization of the allocated set of network communicationresources; determine whether the present utilization satisfies apredefined utilization threshold; and adjust, through the expansion busswitch and in response to a determination that the present utilizationdoes not satisfy the predefined utilization threshold, an amount ofnetwork communication resources in the set to the compute device.

Example 2 includes the subject matter of Example 1, and wherein thecompute engine is further to provide threshold data indicative of theutilization threshold to the set of network communication resources, andwherein to determine whether the present utilization satisfies thepredefined threshold comprises to obtain a notification from the set ofnetwork communication resources indicative of whether the threshold ispresently satisfied.

Example 3 includes the subject matter of any of Examples 1 and 2, andwherein the compute engine is further to obtain the determination thatthe present utilization does not satisfy the predefined utilizationthreshold from one or more telemetry logic units of one or more networkinterface controllers coupled to the resource manager server.

Example 4 includes the subject matter of any of Examples 1-3, andwherein the compute engine is further to obtain service level agreementdata indicative of the predefined utilization threshold to be satisfiedin association with a workload executed by the compute device.

Example 5 includes the subject matter of any of Examples 1-4, andwherein to adjust the amount of network communication resourcescomprises to produce a request to the expansion bus switch to adjust theallocation of the network communication resources of the compute device.

Example 6 includes the subject matter of any of Examples 1-5, andwherein the network communication resources comprise multiple networkinterface controllers, and wherein to adjust the amount of networkcommunication resources comprises to increase the number of networkinterface controllers in the set.

Example 7 includes the subject matter of any of Examples 1-6, andwherein the network communication resources comprise multiple networkinterface controllers, and wherein to adjust the amount of networkcommunication resources comprises to decrease the number of networkinterface controllers in the set.

Example 8 includes the subject matter of any of Examples 1-7, andwherein the compute engine is further to allocate a different amount ofnetwork communication resources to another compute device connected tothe expansion bus switch.

Example 9 includes the subject matter of any of Examples 1-8, andwherein to allocate the set of network communication resources comprisesto allocate a portion of a total network communication capacity of anetwork interface controller to the compute device.

Example 10 includes the subject matter of any of Examples 1-9, andwherein to allocate a set of network communication resources to acompute device through a expansion bus switch comprises to allocate aset of network communication resources to a compute device through aperipheral component interconnect express bus switch.

Example 11 includes the subject matter of any of Examples 1-10, andwherein to obtain the telemetry data comprises to obtain the telemetrydata from the compute device.

Example 12 includes the subject matter of any of Examples 1-11, andwherein to obtain the telemetry data comprises to obtain the telemetrydata from one or more network interface controllers.

Example 13 includes the subject matter of any of Examples 1-12, andwherein the resource manager server is communicatively coupled to one ormore other resource manager servers to cooperatively adjust the amountof network communication resources to be allocated and wherein to adjustthe amount of network communication resources comprises to produce arequest to a second resource manager server that is communicativelycoupled to the switch.

Example 14 includes the subject matter of any of Examples 1-13, andwherein the telemetry data includes physical telemetry data andperformance data provided by one or more performance monitor agents,wherein the physical telemetry data includes power utilization data orthermal data.

Example 15 includes a method comprising allocating, by a resourcemanager server, a set of network communication resources to a computedevice through an expansion bus switch coupled to the compute device andto the network communication resources; obtaining, with the resourcemanager server, telemetry data indicative of a present utilization ofthe allocated set of network communication resources; determining, withthe resource manager server, whether the present utilization satisfies apredefined utilization threshold; and adjusting, with the expansion busswitch and in response to determining that the present utilization doesnot satisfy the predefined utilization threshold, an amount of networkcommunication resources in the set to the compute device.

Example 16 includes the subject matter of Example 15, and furtherincluding providing, with the resource manager server, threshold dataindicative of the utilization threshold to the set of networkcommunication resources, and wherein determining whether the presentutilization satisfies the predefined threshold comprises obtaining anotification from the set of network communication resources indicativeof whether the threshold is presently satisfied.

Example 17 includes the subject matter of any of Examples 15 and 16, andfurther including obtaining, with the resource manager server, thedetermination that the present utilization does not satisfy thepredefined utilization threshold from one or more telemetry logic unitsfrom one or more network interface controllers coupled to the resourcemanager server.

Example 18 includes the subject matter of any of Examples 15-17, andfurther including obtaining, with the resource manager server, servicelevel agreement data indicative of the predefined utilization thresholdto be satisfied in association with a workload executed by the computedevice.

Example 19 includes the subject matter of any of Examples 15-18, andwherein adjusting the amount of network communication resourcescomprises producing a request to the expansion bus switch to adjust theallocation of the network communication resources of the compute device.

Example 20 includes the subject matter of any of Examples 15-19, andwherein the network communication resources comprise multiple networkinterface controllers, and wherein adjusting the amount of networkcommunication resources comprises increasing the number of networkinterface controllers in the set.

Example 21 includes the subject matter of any of Examples 15-20, andwherein the network communication resources comprise multiple networkinterface controllers, and wherein adjusting the amount of networkcommunication resources comprises decreasing the number of networkinterface controllers in the set.

Example 22 includes the subject matter of any of Examples 15-21, andfurther including allocating, with the resource manager server, adifferent amount of network communication resources to another computedevice connected to the expansion bus switch.

Example 23 includes the subject matter of any of Examples 15-22, andwherein allocating the set of network communication resources comprisesallocating a portion of a total network communication capacity of anetwork interface controller to the compute device.

Example 24 includes the subject matter of any of Examples 15-23, andwherein allocating a set of network communication resources to a computedevice through a expansion bus switch comprises allocating a set ofnetwork communication resources to a compute device through a peripheralcomponent interconnect express bus switch.

Example 25 includes the subject matter of any of Examples 15-24, andwherein obtaining the telemetry data comprises obtaining the telemetrydata from the compute device.

Example 26 includes the subject matter of any of Examples 15-25, andwherein obtaining the telemetry data comprises obtaining the telemetrydata from one or more network interface controllers.

Example 27 includes the subject matter of any of Examples 15-26, andwherein the resource manager server is communicatively coupled to one ormore other resource manager servers to cooperatively adjust the amountof network communication resources to be allocated and wherein adjustingthe amount of network communication resources comprises producing arequest to a second resource manager server that is communicativelycoupled to the expansion bus switch.

Example 28 includes the subject matter of any of Examples 15-27, andwherein the telemetry data includes physical telemetry data andperformance data provided by one or more performance monitor agents,wherein the physical telemetry data includes power utilization data orthermal data.

Example 29 includes one or more machine-readable storage mediacomprising a plurality of instructions stored thereon that, in responseto being executed, cause a resource manager server to perform the methodof any of Examples 15-28.

Example 30 includes a resource manager server comprising means forperforming the method of any of Examples 15-28.

Example 31 includes a resource manager server comprising one or moreprocessors; one or more memory devices having stored therein a pluralityof instructions that, when executed by the one or more processors, causethe resource manager server to perform the method of any of Examples15-28.

Example 32 includes a resource manager server comprising allocationmanager circuitry to allocate a set of network communication resourcesto a compute device through an expansion bus switch coupled to thecompute device and to the network communication resources; and networkcommunicator circuitry to obtain telemetry data indicative of a presentutilization of the allocated set of network communication resources;wherein the allocation manager circuitry is further to determine whetherthe present utilization satisfies a predefined utilization threshold;and adjust, through the expansion bus switch and in response to adetermination that the present utilization does not satisfy thepredefined utilization threshold, an amount of network communicationresources in the set to the compute device.

Example 33 includes the subject matter of Example 32, and wherein theallocation manager circuitry is further to provide threshold dataindicative of the utilization threshold to the set of networkcommunication resources, and wherein to determine whether the presentutilization satisfies the predefined threshold comprises to obtain anotification from the set of network communication resources indicativeof whether the threshold is presently satisfied.

Example 34 includes the subject matter of any of Examples 32 and 33, andwherein the allocation manager circuitry is further to obtain thedetermination that the present utilization does not satisfy thepredefined utilization threshold from one or more telemetry logic unitsof one or more network interface controllers coupled to the resourcemanager server.

Example 35 includes the subject matter of any of Examples 32-34, andwherein the allocation manager circuitry is further to obtain servicelevel agreement data indicative of the predefined utilization thresholdto be satisfied in association with a workload executed by the computedevice.

Example 36 includes the subject matter of any of Examples 32-35, andwherein to adjust the amount of network communication resourcescomprises to produce a request to the expansion bus switch to adjust theallocation of the network communication resources of the compute device.

Example 37 includes the subject matter of any of Examples 32-36, andwherein the network communication resources comprise multiple networkinterface controllers, and wherein to adjust the amount of networkcommunication resources comprises to increase the number of networkinterface controllers in the set.

Example 38 includes the subject matter of any of Examples 32-37, andwherein the network communication resources comprise multiple networkinterface controllers, and wherein to adjust the amount of networkcommunication resources comprises to decrease the number of networkinterface controllers in the set.

Example 39 includes the subject matter of any of Examples 32-38, andwherein the allocation manager circuitry is further to allocate adifferent amount of network communication resources to another computedevice connected to the expansion bus switch.

Example 40 includes the subject matter of any of Examples 32-39, andwherein to allocate the set of network communication resources comprisesto allocate a portion of a total network communication capacity of anetwork interface controller to the compute device.

Example 41 includes the subject matter of any of Examples 32-40, andwherein to allocate a set of network communication resources to acompute device through a expansion bus switch comprises to allocate aset of network communication resources to a compute device through aperipheral component interconnect express bus switch.

Example 42 includes the subject matter of any of Examples 32-41, andwherein to obtain the telemetry data comprises to obtain the telemetrydata from the compute device.

Example 43 includes the subject matter of any of Examples 32-42, andwherein to obtain the telemetry data comprises to obtain the telemetrydata from one or more network interface controllers.

Example 44 includes the subject matter of any of Examples 32-43, andwherein the resource manager server is communicatively coupled to one ormore other resource manager servers to cooperatively adjust the amountof network communication resources to be allocated and wherein to adjustthe amount of network communication resources comprises to produce arequest to a second resource manager server that is communicativelycoupled to the switch.

Example 45 includes the subject matter of any of Examples 32-44, andwherein the telemetry data includes physical telemetry data andperformance data provided by one or more performance monitor agents,wherein the physical telemetry data includes power utilization data orthermal data.

Example 46 includes a resource manager server comprising circuitry forallocating a set of network communication resources to a compute devicethrough an expansion bus switch coupled to the compute device and to thenetwork communication resources; circuitry for obtaining telemetry dataindicative of a present utilization of the allocated set of networkcommunication resources; circuitry for determining whether the presentutilization satisfies a predefined utilization threshold; and means foradjusting, with the expansion bus switch and in response to determiningthat the present utilization does not satisfy the predefined utilizationthreshold, an amount of network communication resources in the set tothe compute device.

Example 47 includes the subject matter of Example 46, and furtherincluding circuitry for providing threshold data indicative of theutilization threshold to the set of network communication resources, andwherein the circuitry for determining whether the present utilizationsatisfies the predefined threshold comprises circuitry for obtaining anotification from the set of network communication resources indicativeof whether the threshold is presently satisfied.

Example 48 includes the subject matter of any of Examples 46 and 47, andfurther including circuitry for obtaining the determination that thepresent utilization does not satisfy the predefined utilizationthreshold from one or more telemetry logic units from one or morenetwork interface controllers coupled to the resource manager server.

Example 49 includes the subject matter of any of Examples 46-48, andfurther including circuitry for obtaining service level agreement dataindicative of the predefined utilization threshold to be satisfied inassociation with a workload executed by the compute device.

Example 50 includes the subject matter of any of Examples 46-49, andwherein the means for adjusting the amount of network communicationresources comprises circuitry for producing a request to the expansionbus switch to adjust the allocation of the network communicationresources of the compute device.

Example 51 includes the subject matter of any of Examples 46-50, andwherein the network communication resources comprise multiple networkinterface controllers, and wherein the means for adjusting the amount ofnetwork communication resources comprises circuitry for increasing thenumber of network interface controllers in the set.

Example 52 includes the subject matter of any of Examples 46-51, andwherein the network communication resources comprise multiple networkinterface controllers, and wherein the means for adjusting the amount ofnetwork communication resources comprises circuitry for decreasing thenumber of network interface controllers in the set.

Example 53 includes the subject matter of any of Examples 46-52, andfurther including circuitry for allocating a different amount of networkcommunication resources to another compute device connected to theexpansion bus switch.

Example 54 includes the subject matter of any of Examples 46-53, andwherein the circuitry for allocating the set of network communicationresources comprises circuitry for allocating a portion of a totalnetwork communication capacity of a network interface controller to thecompute device.

Example 55 includes the subject matter of any of Examples 46-54, andwherein the circuitry for allocating a set of network communicationresources to a compute device through a expansion bus switch comprisescircuitry for allocating a set of network communication resources to acompute device through a peripheral component interconnect express busswitch.

Example 56 includes the subject matter of any of Examples 46-55, andwherein the circuitry for obtaining the telemetry data comprisescircuitry for obtaining the telemetry data from the compute device.

Example 57 includes the subject matter of any of Examples 46-56, andwherein the circuitry for obtaining the telemetry data comprisescircuitry for obtaining the telemetry data from one or more networkinterface controllers.

Example 58 includes the subject matter of any of Examples 46-57, andwherein the resource manager server is communicatively coupled to one ormore other resource manager servers to cooperatively adjust the amountof network communication resources to be allocated and wherein the meansfor adjusting the amount of network communication resources comprisescircuitry for producing a request to a second resource manager serverthat is communicatively coupled to the expansion bus switch.

Example 59 includes the subject matter of any of Examples 46-58, andwherein the telemetry data includes physical telemetry data andperformance data provided by one or more performance monitor agents,wherein the physical telemetry data includes power utilization data orthermal data.

Example 60 includes a resource manager server comprising a computeengine to allocate a set of network communication resources to a computedevice; obtain telemetry data indicative of a present utilization of theallocated set of network communication resources; determine whether thepresent utilization satisfies a predefined utilization threshold; andadjust, in response to a determination that the present utilization doesnot satisfy the predefined utilization threshold, an amount of networkcommunication resources in the set to the compute device.

Example 61 includes the subject matter of Example 60, and wherein toadjust the amount of network communication resources comprises to adjusta number of network links to or from the compute device.

Example 62 includes the subject matter of any of Examples 60 and 61, andwherein to adjust the amount of network communication resourcescomprises to adjust a speed of one or more network links provided by thenetwork communication resources.

Example 63 includes the subject matter of any of Examples 60-62, andwherein to adjust the amount of network communication resourcescomprises to adjust a traffic shaping parameter associated with thenetwork communication resources.

Example 64 includes a method comprising allocating, by a resourcemanager server, a set of network communication resources to a computedevice; obtaining, by the resource manager server, telemetry dataindicative of a present utilization of the allocated set of networkcommunication resources; determining, by the resource manager server,whether the present utilization satisfies a predefined utilizationthreshold; and adjusting, by the resource manager server and in responseto a determination that the present utilization does not satisfy thepredefined utilization threshold, an amount of network communicationresources in the set to the compute device.

Example 65 includes the subject matter of Example 64, and whereinadjusting the amount of network communication resources comprisesadjusting a number of network links to or from the compute device.

Example 66 includes the subject matter of any of Examples 64 and 65, andwherein adjusting the amount of network communication resourcescomprises adjusting a speed of one or more network links provided by thenetwork communication resources.

Example 67 includes the subject matter of any of Examples 64-66, andwherein adjusting the amount of network communication resourcescomprises adjusting a traffic shaping parameter associated with thenetwork communication resources.

Example 68 includes one or more machine-readable storage mediacomprising a plurality of instructions stored thereon that, in responseto being executed, cause a resource manager server to perform the methodof any of Examples 64-67.

Example 69 includes a resource manager server comprising means forperforming the method of any of Examples 64-67.

Example 70 includes a resource manager server comprising one or moreprocessors; one or more memory devices having stored therein a pluralityof instructions that, when executed by the one or more processors, causethe resource manager server to perform the method of any of Examples64-67.

Example 71 includes a resource manager server comprising allocationmanager circuitry to allocate a set of network communication resourcesto a compute device; and network communicator circuitry to obtaintelemetry data indicative of a present utilization of the allocated setof network communication resources; wherein the allocation managercircuitry is further to determine whether the present utilizationsatisfies a predefined utilization threshold; and adjust, in response toa determination that the present utilization does not satisfy thepredefined utilization threshold, an amount of network communicationresources in the set to the compute device.

Example 72 includes the subject matter of Example 71, and wherein toadjust the amount of network communication resources comprises to adjusta number of network links to or from the compute device.

Example 73 includes the subject matter of any of Examples 71 and 72, andwherein to adjust the amount of network communication resourcescomprises to adjust a speed of one or more network links provided by thenetwork communication resources.

Example 74 includes the subject matter of any of Examples 71-73, andwherein to adjust the amount of network communication resourcescomprises to adjust a traffic shaping parameter associated with thenetwork communication resources.

Example 75 includes a resource manager server comprising circuitry forallocating a set of network communication resources to a compute device;circuitry for obtaining telemetry data indicative of a presentutilization of the allocated set of network communication resources;circuitry for determining whether the present utilization satisfies apredefined utilization threshold; and means for adjusting, in responseto a determination that the present utilization does not satisfy thepredefined utilization threshold, an amount of network communicationresources in the set to the compute device.

Example 76 includes the subject matter of Example 75, and wherein themeans for adjusting the amount of network communication resourcescomprises circuitry for adjusting a number of network links to or fromthe compute device.

Example 77 includes the subject matter of any of Examples 75 and 76, andwherein the means for adjusting the amount of network communicationresources comprises circuitry for adjusting a speed of one or morenetwork links provided by the network communication resources.

Example 78 includes the subject matter of any of Examples 75-77, andwherein the means for adjusting the amount of network communicationresources comprises circuitry for adjusting a traffic shaping parameterassociated with the network communication resources.

The invention claimed is:
 1. A resource manager server comprising: aprocessor circuit to: allocate a portion of network communicationresources from a collection of network communication resources to acompute device that hosts circuitry to execute a workload, thecollection of network communication resources separately coupled witheach other through a coherent memory link switch, each networkcommunication resource in the collection of network communicationresources capable of separately coupling with the compute device throughthe coherent memory link switch; obtain telemetry data indicative of autilization of the allocated portion of network communication resourceswhile the circuitry executes the workload; and adjust, through thecoherent memory link switch, an amount of network communicationresources included in the allocated portion of network communicationresources based on the utilization of the allocated portion indicated inthe obtained telemetry data.
 2. The resource manager server of claim 1,further comprising the processor circuit to: provide threshold dataindicative of a utilization threshold to the allocated portion ofnetwork communication resources, and wherein to adjust the amount ofnetwork communication resources is based on the obtained telemetry dataincluding at least one notification from the allocated portion ofnetwork communication resources indicative of whether the utilizationthreshold is presently satisfied.
 3. The resource manager server ofclaim 2, comprising the at least one notification indicates that theutilization does not satisfy the utilization threshold, wherein the atleast one notification was generated by one or more telemetry logicunits of one or more network interface controllers included in theallocated portion of network communication resources.
 4. The resourcemanager server of claim 2, wherein the processor circuit is further toobtain service level agreement data indicative of the utilizationthreshold to be satisfied while the circuitry hosted by the computedevice executes the workload.
 5. The resource manager server of claim 1,wherein to adjust the amount of network communication resourcescomprises to produce a request to the coherent memory link switch toadjust the allocated portion of network communication resourcesallocated to the compute device.
 6. The resource manager server of claim1, the collection of network communication resources includes multiplenetwork interface controllers, wherein to adjust the amount of networkcommunication resources included in the allocated portion of networkcommunication resources comprises to increase a number of networkinterface controllers in the allocated portion.
 7. The resource managerserver of claim 1, the collection of network communication resourcesincludes multiple network interface controllers, wherein to adjust theamount of network communication resources included in the allocatedportion of network communication resources comprises to decrease anumber of network interface controllers in the allocated portion.
 8. Theresource manager server of claim 7, wherein the processor circuit isfurther to reallocate the decreased number of network interfacecontrollers previously allocated to the compute device to a secondcompute device, each network communication resource in the collection ofnetwork communication resources also capable of separately coupling withthe second compute device through the coherent memory link switch, thesecond compute device to host second circuitry to execute a secondworkload.
 9. The resource manager server of claim 1, wherein theprocessor circuit is further to allocate a second portion of networkcommunication resources from the collection of network communicationresources to a second compute device, each network communicationresource in the collection of network communication resources alsocapable of separately coupling with the second compute device throughthe coherent memory link switch, the second compute device to hostsecond circuitry to execute a second workload.
 10. The resource managerserver of claim 1, wherein to allocate the portion of networkcommunication resources from the collection of network communicationresources comprises to allocate a first portion of a total networkcommunication capacity of a network interface controller included in thecollection of network communication resources to the compute device. 11.The resource manager server of claim 1, the coherent memory link switchcomprises a peripheral component interconnect express bus switch. 12.The resource manager server of claim 1, wherein to obtain the telemetrydata comprises to obtain the telemetry data from the compute device. 13.The resource manager server of claim 1, wherein to obtain the telemetrydata comprises to obtain the telemetry data from one or more networkinterface controllers included in the allocated portion of networkcommunication resources.
 14. The resource manager server of claim 1,wherein the resource manager server is communicatively coupled with oneor more other resource manager servers to cooperatively adjust theamount of network communication resources of the collection of networkcommunication resources to be separately allocated to a plurality ofcompute devices and wherein to adjust the amount of networkcommunication resources included in the portion allocated to the computedevice comprises the processor circuit to produce a request to a secondresource manager server that is communicatively coupled with thecoherent memory link switch, the request to indicate a need to adjustthe amount of network communication resources include in the portionallocated to the compute device.
 15. The resource manager server ofclaim 1, wherein the telemetry data includes physical telemetry data andperformance data provided by one or more performance monitor agents,wherein the physical telemetry data includes power utilization data orthermal data.
 16. One or more non-transitory machine-readable storagemedia comprising a plurality of instructions stored thereon that, inresponse to being executed, cause a resource manager server to: allocatea portion of network communication resources from a collection ofnetwork communication resources to a compute device that hosts circuitryto execute a workload, the collection of network communication resourcesseparately coupled with each other through a coherent memory linkswitch, each network communication resource in the collection of networkcommunication resources capable of separately coupling with the computedevice through the coherent memory link switch; obtain telemetry dataindicative of a utilization of the allocated portion of networkcommunication resources while the circuitry executes the workload; andadjust, through the coherent memory link switch, an amount of networkcommunication resources included in the allocated portion of networkcommunication resources based on the utilization of the allocatedportion indicated in the obtained telemetry data.
 17. The one or morenon-transitory machine-readable storage media of claim 16, wherein theplurality of instructions, when executed, further cause the resourcemanager server to: provide threshold data indicative of a utilizationthreshold to the allocated portion of network communication resources,and wherein to adjust the amount of network communication resources isbased on the obtained telemetry data including at least one notificationfrom the allocated portion of network communication resources indicativeof whether the utilization threshold is presently satisfied.
 18. The oneor more non-transitory machine-readable storage media of claim 17,comprising the at least one notification indicates that the utilizationdoes not satisfy the utilization threshold, wherein the at least onenotification was generated by one or more telemetry logic units of oneor more network interface controllers included in the allocated portionof network communication resources.
 19. The one or more non-transitorymachine-readable storage media of claim 17, wherein the plurality ofinstructions, when executed, further cause the resource manager serverto obtain service level agreement data indicative of the utilizationthreshold to be satisfied while the circuitry hosted by the computedevice executes the workload.
 20. The one or more non-transitorymachine-readable storage media of claim 16, wherein to adjust the amountof network communication resources comprises to produce a request to thecoherent memory link switch to adjust the allocated portion of networkcommunication resources allocated to the compute device.
 21. The one ormore non-transitory machine-readable storage media of claim 16, thecollection of network communication resources includes multiple networkinterface controllers, wherein to adjust the amount of networkcommunication resources included in the allocated portion of networkcommunication resources comprises to increase a number of networkinterface controllers in the allocated portion.
 22. The one or morenon-transitory machine-readable storage media of claim 16, wherein thecollection of network communication resources includes multiple networkinterface controllers, and wherein to adjust the amount of networkcommunication resources included in the allocated portion of networkcommunication resources comprises to decrease a number of networkinterface controllers in the allocated portion.
 23. The one or morenon-transitory machine-readable storage media of claim 22, the pluralityof instructions to further cause the resource manager server toreallocate the decreased number of network interface controllerspreviously allocated to the compute device to a second compute device ,each network communication resource in the collection of networkcommunication resources also capable of separately coupling with thesecond compute device through the coherent memory link switch, thesecond compute device to host second circuitry to execute a secondworkload.
 24. The one or more non-transitory machine-readable storagemedia of claim 16, wherein the plurality of instructions, when executed,further cause the resource manager server to allocate a second portionof network communication resources from the collection of networkcommunication resources to a second compute device, each networkcommunication resource in the collection of network communicationresources also capable of separately coupling with the second computedevice through the coherent memory link switch, the second computedevice to host second circuitry to execute a second workload.
 25. Theone or more non-transitory machine-readable storage media of claim 16,wherein to allocate the portion of network communication resources fromthe collection of network communication resources comprises to allocatea first portion of a total network communication capacity of a networkinterface controller included in the collection of network communicationresources to the compute device.
 26. The one or more non-transitorymachine-readable storage media of claim 16, the coherent memory linkswitch comprises a peripheral component interconnect express bus switch.27. A method comprising: allocating a portion of network communicationresources from a collection of network communication resources to acompute device that hosts circuitry to execute a workload, thecollection of network communication resources separately coupled witheach other through a coherent memory link switch, each networkcommunication resource in the collection of network communicationresources capable of separately coupling with the compute device throughthe coherent memory link switch; obtaining telemetry data indicative ofa utilization of the allocated portion of network communicationresources while the circuitry executes the workload; and adjusting,through the coherent memory link switch, an amount of networkcommunication resources included in the allocated portion of networkcommunication resources based on the utilization of the allocatedportion indicated in the obtained telemetry data.
 28. The method ofclaim 27, further comprising: providing threshold data indicative of autilization threshold to the allocated portion of network communicationresources, and wherein adjusting the amount of network communicationresources is based on the obtained telemetry data including at least onenotification from the allocated portion of network communicationresources indicative of whether the utilization threshold is presentlysatisfied.
 29. The method of claim 28, comprising the at least onenotification indicates that utilization does not satisfy the utilizationthreshold, wherein the at least one notification was generated by one ormore telemetry logic units of one or more network interface controllersincluded in the allocated portion of network communication resources.30. One or more non-transitory machine-readable storage media comprisinga plurality of instructions stored thereon that, in response to beingexecuted, cause a system to: allocate one or more network interfacecontrollers (NICs) to a compute device that hosts circuitry to execute aworkload, the one or more NICs included in a collection of NICs locatedremote to the compute device, the collection of NICs to be separatelycoupled with each other through a coherent memory link switch, each NICin the collection of NICs also capable of separately coupling with thecompute device through the coherent memory link switch; and obtaintelemetry data that indicates a utilization of the allocated one or moreNICs while the circuitry executes the workload; and adjust, through thecoherent memory link switch, a number of NICs included in the allocatedone or more NICs based on the utilization indicated in the obtainedtelemetry data.
 31. The one or more non-transitory machine-readablestorage media of claim 30, wherein the plurality of instructions, whenexecuted, further cause the system to: provide threshold data indicativeof a utilization threshold to the allocated one or more NICs, andwherein to adjust the number of NICs is based on the obtained telemetrydata including at least one notification from the allocated one or moreNICs indicative of whether the utilization threshold is presentlysatisfied.
 32. The one or more non-transitory machine-readable storagemedia of claim 30, the coherent memory link switch comprises aperipheral component interconnect express bus switch.
 33. The one ormore non-transitory machine-readable storage media of claim 30, whereinto adjust the number of NICs included in the allocated one or more NICscomprises to decrease the number of NICs included in the allocated oneor more NICs.
 34. The one or more non-transitory machine-readablestorage media of claim 33, the plurality of instructions to furthercause the system to reallocate the decreased number of NICs previouslyallocated to the compute device to a second compute device, each NIC inthe collection of NICs also capable of separately coupling with thesecond compute device through the coherent memory link switch, thesecond compute device to host second circuitry to execute a secondworkload, wherein the collection of NICs is located remote to the secondcompute device.